Conversation
The release metadata and package manifests now point to the next patch version so publish pipelines can ship the updated tarball. Constraint: User requested version bump and git publication in this turn Rejected: Skip README release notes update | violates repository release hygiene for version bumps Confidence: high Scope-risk: narrow Reversibility: clean Directive: Keep package.json/package-lock.json and README release notes in sync on every version bump Tested: node --check bin/multiagent-safety.js Tested: node --test test/metadata.test.js Tested: npm pack --dry-run Tested: npm test (fails pre-existing setup baseline: requireValue/parseDoctorArgs undefined across many install tests) Not-tested: end-to-end npm publish to registry
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated by scripts/agent-branch-finish.sh (PR flow).